Release 10.1A: OpenEdge Reporting:
Query/Results Administration and Development

Export solutions in Results

Results provides a robust set of standard export formats, but you can also develop your own standard export format. There are two basic techniques for implementing a standard export format for use at a user site:

Edit the existing Sample Export format.
Edit the results.l file to define a new export format.

This section describes the Sample Export Format. For information about the contents of the results.l file, see Appendix C "Results Files."

The Sample Export format is one of the default standard export formats and performs an export using the default Progress export format. The Progress source procedure that implements the Sample Export format is u-export.p and is located in the aderes product directory.

You can edit the u-export.p procedure and code your own export solution. Note that the u-export.p procedure executes once for each field defined for export in the query. These fields are listed in the qbf–rcn API shared variable for the active query. The u-export.p procedure defines several input parameters that pass information about the current export field from Results to the procedure. Descriptions for each of these input parameters are located in the comment text of the u-export.p procedure.

The body of the u-export.p procedure builds an EXPORT statement using the input parameter values. The u-export.p procedure uses the PUT statement to write the EXPORT statement to a temporary file that Results executes to export data from the query. For more information about the EXPORT and PUT statements, see the OpenEdge Development: Progress 4GL Reference .

If you copy and edit the u-export.p file, make sure that the new procedure is located in a directory that is listed in the PROPATH before the product directory (DLC).